Authorizing a payment with a multi-function transaction card

ABSTRACT

A multi-function transaction card may include a card body having dimensions that are in accordance with a standard for transaction cards, an output device on the card body, and a secure element within the card body. The multi-function transaction card may pair, via a wireless connection, the multi-function transaction card with a terminal. The multi-function transaction card may receive, from the terminal, information associated with a transaction. The multi-function transaction card may generate, based on the information associated with the transaction, and using a cryptographic key, an authorization request cryptogram (ARQC), wherein the cryptographic key is stored in the secure element. The multi-function transaction card may generate, based on the ARQC, a machine-readable code. The multi-function transaction card may display, using the output device, the machine-readable code.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/853,066, filed Apr. 20, 2020, which is incorporated herein byreference.

BACKGROUND

A contactless transaction involves the use of a transaction card (e.g.,a credit card, a debit card, and/or the like) and a transaction terminal(e.g., a point of sale (PoS) terminal) without a need for thetransaction card to contact the transaction terminal to process thetransaction. The contactless transaction may require authorization toensure an accurate and secure payment to complete the contactlesstransaction.

SUMMARY

According to some implementations, a multi-function transaction card mayinclude a card body having dimensions that are in accordance with astandard for transaction cards; an output device on the card body; asecure element within the card body; one or more memories within thecard body; and one or more processors within the card body, wherein theone or more processors are communicatively coupled to the one or morememories, wherein the one or more processors are configured to: pair,via a wireless connection, the multi-function transaction card with aterminal; receive, from the terminal, information associated with atransaction; generate, based on the information associated with thetransaction, and using a cryptographic key, an authorization requestcryptogram (ARQC), wherein the cryptographic key is stored in the secureelement; generate, based on the ARQC, a machine-readable code; anddisplay, using the output device, the machine-readable code.

According to some implementations, a method may include receiving, by amulti-function transaction card and from a terminal, informationassociated with a transaction, wherein the multi-function transactioncard has dimensions that are in accordance with a standard fortransaction cards; generating, by the multi-function transaction card,based on the information associated with the transaction, and using acryptographic key, an authorization request cryptogram (ARQC), whereinthe cryptographic key is stored in a secure element, and wherein themulti-function transaction card comprises the secure element;generating, by the multi-function transaction card and based on theARQC, an optical pattern; and outputting, by the multi-functiontransaction card and using an output device, the optical pattern.

According to some implementations, a non-transitory computer-readablemedium may store one or more instructions. The one or more instructions,when executed by one or more processors, may cause the one or moreprocessors to: pair, via a wireless connection, a multi-functiontransaction card with a terminal; receive, from the terminal,information associated with a transaction; generate, based on theinformation associated with the transaction and using a cryptographickey, an authorization request cryptogram (ARQC), wherein thecryptographic key is stored in a secure element in the multi-functiontransaction card; generate, based on the ARQC, a pulsed light pattern;and cause an output device of the multi-function transaction card toemit, based on the pulsed light pattern, a series of light pulses.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A-1D are diagrams of one or more example implementationsdescribed herein.

FIG. 2 is a diagram of an example environment in which systems and/ormethods described herein may be implemented.

FIG. 3 is a diagram of example components of one or more devices of FIG.2 .

FIGS. 4-6 are flowcharts of example processes for authorizing a paymentwith a multi-function transaction card.

DETAILED DESCRIPTION

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings may identify the same or similar elements.

To conduct a contactless transaction between a paying device (e.g., amobile device, a multi-function transaction card, and/or the like) and areceiving device (e.g., another mobile device, a terminal, anothermulti-function transaction card, and/or the like), the paying device andthe receiving device may communicate using near field communication(NFC). However, some paying devices and/or receiving devices do notpossess NFC capability. Additionally, the NFC capability of a payingdevice and/or a receiving device may malfunction. Identifying the NFCissue, investigating the NFC issue, and conducting the contactlesstransaction by a different method consumes additional computingresources (e.g., processing resources, memory resources, powerresources, communication resources, and/or the like) and/or networkresources. Additionally, as a transaction may transmit sensitiveinformation from the paying device to the receiving device, thedifferent method of conducting the transaction may increase the risk offraudulent activity related to the transaction. Identifying,investigating, and/or correcting any fraudulent activity consumesadditional computing resources and/or network resources.

Some implementations described herein provide a multi-functiontransaction card that provides a reliable and secure method ofauthorizing a payment. As described herein, the multi-functiontransaction card may pair with a terminal, and may receive, from theterminal, information associated with a transaction (e.g., an amount ofthe transaction, merchant information, and/or the like). In someimplementations, the multi-function transaction card may generate, basedon the information associated with the transaction and using acryptographic key stored in a secure element in the multi-functiontransaction card, an authorization request cryptogram (ARQC). In someimplementations, the multi-function transaction card may generate, basedon the ARQC, an optical pattern (e.g., a machine-readable code (e.g., aQR code), a pulsed light pattern, and/or the like), and may output,using an output device, the optical pattern. For example, themulti-function transaction card may display a QR code, and the terminalmay capture an image of the QR code. By generating the optical patternbased on the ARQC, the multi-function transaction card may reduce therisk of fraudulent activity and conserve computing resources (e.g.,processing resources, memory resources, power resources, communicationresources, and/or the like) and/or network resources that would haveotherwise been used to identify, investigate, and/or correct fraudulentactivity. Additionally, or alternatively, the multi-function transactioncard may authorize payments without the use of a near-fieldcommunication (NFC) chip, which may reduce a cost of manufacturing ofthe multi-function transaction card and/or permit the multi-functiontransaction card to authorize payments when an NFC chip is not working,the terminal does not have an NFC chip, and/or the like.

FIGS. 1A-1D are diagrams of one or more example implementations 100described herein. As shown in FIGS. 1A-1D, example implementation(s) 100may include a multi-function transaction card (e.g., associated with amerchant and/or a consumer), a user device, and/or a transactionbackend. The multi-function transaction card may wirelessly receiveinformation associated with a transaction from a terminal. The terminalmay be a transaction terminal (e.g., a point of sale (PoS) terminal), amulti-function transaction card associated with the merchant, a userdevice associated with the merchant, and/or the like.

The multi-function transaction card may include a card body havingdimensions that are in accordance with a standard. In someimplementations, the multi-function transaction card is implemented in aform factor that is in accordance with a standard for transaction cards(e.g., International Organization for Standardization/InternationalElectrotechnical Commission (ISO/IEC) 7810 ID-1). In someimplementations, the card body may have dimensions that are inaccordance with a standard that is associated with payment cards (e.g.,credit cards, debit cards, and/or the like)—e.g., ISO/IEC 7810 ID-1(e.g., a card body having a size of 85.60 millimeters×53.98 millimeters(3.370 inches×2.125 inches) and rounded corners with a radius of 2.88millimeters to 3.48 millimeters).

As shown in FIG. 1A, the multi-function transaction card may include,among other components (e.g., as described elsewhere herein), acontroller, a sensor, a secure element, and/or an output device. In someimplementations, the multi-function transaction card may include aprocessor, such as a microcontroller that is capable of executingapplication logic. In some implementations, the secure element may beincluded in a transaction integrated circuit (IC) chip (e.g., aEUROPAY®, MASTERCARD®, VISA® (EMV) chip).

As described in more detail below, the multi-function transaction cardmay be capable of functioning as both a transaction card reader (e.g., areader that reads other transaction cards, such as payment cards (e.g.,credit cards, debit cards, other multi-function transaction cards,and/or the like), to receive payments), and as a payment card (e.g., acard that submits payments to other transaction card readers, such astransaction terminals, user devices, and/or other multi-functiontransaction cards). In some implementations, the multi-functiontransaction card may include application logic (e.g., stored in memoryin the secure element), such as EMV-based application logic, configuredto process card data received from contactless transaction cards, andapplication logic (e.g., also stored in memory in the secure element)configured to provide card data to transaction terminals for processing.Thus, a user of the multi-function transaction card may, at times, actas a merchant and accept payments from a consumer's contactlesstransaction card and, at other times, act as a consumer to submitpayments using the multi-function transaction card.

As shown in FIG. 1A, a multi-function transaction card may be associatedwith a merchant (hereinafter referred to as a merchant multi-functiontransaction card). The merchant may be a provider of goods and/orservices. The merchant may conduct a transaction with a consumer using auser device and/or a terminal. In some implementations, the user deviceand the terminal may be the same device (e.g., a single user device, asingle multi-function transaction card, a single PoS terminal, and/orthe like). In some implementations, the user device and/or the terminalmay communicate with a transaction backend for executing transactions.For example, the user device may receive transaction information. Thetransaction information may include product information (e.g., a productname, stock keeping unit (SKU) identifier associated with a product,product identifier, and/or the like) for one or more products (e.g., oneor more goods and/or services) associated with the transaction, atransaction amount (e.g., a total amount the merchant is charging theconsumer for the transaction), merchant information associated with themerchant (e.g., a merchant name, a merchant identifier, and/or thelike), a transaction date (e.g., a date on which the transaction isexecuted), metadata associated with the transaction (e.g., a terminalcountry code, a transaction currency code, a transaction type, and/orthe like), and/or the like.

As shown by reference number 102, the terminal may pair with the userdevice. For this example, assume that the terminal is a merchantmulti-function transaction card. The merchant multi-function transactioncard may pair (e.g., establish a secure connection to enablecommunication) with the user device using a communication protocol(e.g., a personal area network protocol, such as a Bluetooth-basednetwork protocol and/or the like) to communicate via a wirelessconnection (such as a Bluetooth connection, a Wi-Fi connection, acellular connection, a near field communication (NFC) connection, and/orthe like).

The wireless connection may enable the merchant multi-functiontransaction card to receive information from the user device andtransmit information to the user device. For example, the merchantmulti-function transaction card may receive transaction informationassociated with a transaction from the user device via the wirelessconnection. The transaction information may be stored by the merchantmulti-function transaction card.

A different multi-function transaction card may be associated with aconsumer (hereinafter referred to as a consumer multi-functiontransaction card). The consumer may be associated with the transaction,such as a purchaser of a good or service offered by the merchant. Asshown by reference number 104, the consumer multi-function transactioncard may pair (e.g., establish a secure connection to enablecommunication) with the merchant multi-function transaction card deviceusing a communication protocol (e.g., a personal area network protocol,such as a Bluetooth-based network protocol and/or the like) tocommunicate via a wireless connection (such as a Bluetooth connection, aWi-Fi connection, a cellular connection, an NFC connection, and/or thelike).

The consumer multi-function transaction card may receive informationfrom the merchant multi-function transaction card via the wirelessconnection. For example, the consumer multi-function transaction cardmay receive the transaction information associated with the transactionfrom the merchant multi-function transaction card. The transactioninformation may be stored by the consumer multi-function transactioncard. In some implementations, the consumer multi-function transactioncard may receive the transaction information from the user deviceassociated with the merchant, such as via a wireless connection.

In some implementations, the merchant multi-function transaction cardmay request authorization from the consumer multi-function transactioncard to execute the transaction. The request for authorization may beincluded in the transaction information transmitted to the consumermulti-function transaction card from the merchant multi-functiontransaction card. Alternatively, the request for authorization may betransmitted separate from the transaction information (e.g., before thetransaction information or after the transaction information)transmitted to the consumer multi-function transaction card from themerchant multi-function transaction card. The request for authorizationmay include a request for the consumer multi-function transaction cardto provide information identifying a transaction account (e.g., a bankaccount, an expense account, a credit account, and/or the like)associated with the consumer and/or the consumer multi-functiontransaction card to be used to execute the transaction.

As further shown in FIG. 1A, and by reference number 106, the consumermulti-function transaction card may generate an authorization requestcryptogram (ARQC). The consumer multi-function transaction card maygenerate the ARQC in response to receiving the transaction informationand/or the request for authorization from the merchant multi-functiontransaction card. The ARQC may be a cryptogram generated based on thetransaction information.

In some implementations, the consumer multi-function transaction cardmay receive cryptographic keys (e.g., public keys) that the secureelement of the consumer multi-function transaction card can use. Forexample, the consumer multi-function transaction card may receive acryptographic key from the merchant multi-function transaction card(hereinafter referred to as “the session key”). The session key may beassociated with the transaction (e.g., the session key may be unique tothe transaction). The session key may be generated based on astandardized scheme (e.g., an EMV scheme).

In some implementations, a cryptographic key (hereinafter referred to as“the card key”) may be stored by the consumer multi-function transactioncard. In some implementations, the card key is stored by the secureelement of the consumer multi-function transaction card. In someimplementations, the card key is stored within the secure element of theconsumer multi-function transaction card by one or more memories of theconsumer multi-function transaction card. The card key may be associatedwith the consumer multi-function transaction card (e.g., the card keymay be unique to the consumer multi-function transaction card). The cardkey may be generated based on a standardized scheme (e.g., an EMVscheme). The card key may be generated based on a master key associatedwith the issuer of the consumer multi-function transaction card. Thecard key may be generated and/or stored within the secure element at atime of manufacture or at a time of issuance of the consumermulti-function transaction card.

The ARQC may be generated based on the transaction informationassociated with the transaction. The transaction information that theARQC is based on may be the transaction information received from themerchant multi-function transaction card (e.g., product information forone or more products associated with the transaction, a transactionamount of the transaction, merchant information associated with themerchant, a transaction date of the transaction, metadata associatedwith the transaction, and/or the like). In some implementations, thetransaction information that the ARQC is based on may includeinformation associated with the consumer multi-function transactioncard, such as an identifier associated with the consumer multi-functiontransaction card, a transaction account identifier associated with atransaction account of the consumer, an identifier of the issuer of theconsumer multi-function transaction card, and/or the like.

The consumer multi-function transaction card may generate the ARQC basedon the transaction information and using the card key. In someimplementations, the consumer multi-function transaction card mayencrypt (e.g., using a hash function) the transaction information usingthe card key, resulting in the ARQC. In some implementations, the ARQCmay be a 16-character hexadecimal ARQC. In some implementations, theARQC may take another form. The ARQC may be generated based on astandardized scheme (e.g., an EMV scheme) associated with the consumermulti-function transaction card. The standardized scheme used togenerate the ARQC may be based on the issuer of the consumermulti-function transaction card.

The ARQC may be used to provide authorization for a transaction. TheARQC may be a digital signature of the transaction information. Forexample, a consumer may wish to conduct a transaction with a merchant.The merchant may provide transaction information associated with thetransaction to the consumer (e.g., via the user device, terminal,merchant multi-function transaction card, and/or consumer multi-functiontransaction card, as described herein). The consumer may agree to theterms of the transaction (such as the transaction amount and/or thelike) and provide authorization for the transaction, such as via theconsumer multi-function transaction card. The ARQC may be included in anauthorization message sent from the consumer multi-function transactioncard to the terminal (e.g., the merchant multi-function transactioncard, a user device associated with the merchant, and/or the like) toverify that the consumer authorized the transaction.

As shown in FIG. 1B, and by reference number 108, the consumermulti-function transaction card may generate, based on the ARQC, anoptical pattern (e.g., a machine-readable code, a pulsed light pattern,and/or the like). The optical pattern may be generated such that whenanother device interprets and/or processes the optical pattern, theother device receives information that includes the ARQC. In someimplementations, the optical pattern may be a machine-readable code. Themachine-readable code may be a Quick Response (QR) code, a matrixbarcode, a one-dimensional barcode, and/or the like. In someimplementations, the optical pattern may be a light pattern, such as apulsed light pattern (e.g., a light pattern generated using pulse-widthmodulation). The light pattern may utilize visible light communication(VLC) technology to communicate information. The light pattern mayutilize an intensity modulation-based modulation scheme, such as colorshift keying (CSK). CSK may allow for wireless communication ofinformation based on color variation emitted by a tri-color(red-blue-green (RBG)) LED. In some implementations, the light patternmay include non-visible light.

The consumer multi-function transaction card may include an outputdevice for displaying the optical pattern. The output device may be adot matrix display, an electronic ink display, a light emitting diode(LED) display, and/or the like. The output device may display theoptical pattern as the machine-readable code and/or the light pattern.In some implementations, the output device may display the opticalpattern as a combination of both a machine-readable code and a lightpattern. For example, a first portion of information (e.g., theinformation that includes the ARQC) may be communicated via themachine-readable code and a second portion of the information may becommunicated via the light pattern. In this way, if either the firstportion or the second portion was to be intercepted by a maliciousentity, the malicious entity would not gain access to all of theinformation and, thus, would not be able to recreate the ARQC. Asanother example, the same information (e.g., the information thatincludes the ARQC) may be communicated via the machine-readable code andvia the light pattern. In this way, more flexibility is provided interms of how the information may be received by a receiving device.

As shown by reference number 110, the consumer multi-functiontransaction card may display the generated machine-readable code usingthe output device. The output device of the consumer multi-functiontransaction card may display the machine-readable code. In someimplementations, the output device may display the machine-readable codeon the surface of the consumer multi-function transaction card.

As shown by reference number 112, the consumer multi-functiontransaction card may emit a series of light pulses associated with theoptical pattern. The output device of the consumer multi-functiontransaction card may emit the series of light pulses. The output deviceof the consumer multi-function transaction card may emit the series oflight pulses using pulse-width modulation.

In some implementations, the consumer multi-function transaction cardmay be configured to automatically display the optical pattern. In someimplementations, the consumer multi-function transaction card may beconfigured to display the optical pattern in response to receiving therequest for authorization and/or the transaction information from theterminal (e.g., the merchant multi-function transaction card, the userdevice, and/or the like). In some implementations, the consumermulti-function transaction card may be configured to display the opticalpattern in response to pairing, via the wireless connection, with theterminal. In some implementations, the consumer multi-functiontransaction card may be configured to display the optical pattern inresponse to the generation of the ARQC.

In some implementations, the consumer multi-function transaction cardmay be configured to display the optical pattern in response to aconsumer input. The consumer input may be a touch input. The touch inputmay relate to a pressure of a touch (e.g., an amount of force applied tothe consumer multi-function transaction card by the consumer), aduration of a touch (e.g., an amount of time that the consumer remainedin contact with the consumer multi-function transaction card), a tap, aswipe, a pattern of motion (e.g., a circular motion, a triangularmotion, a rectangular motion, etc.), a rocking touch, a surface area ofa touch, an alternating touch (e.g., simultaneous swipes to the frontside and the back side of the consumer multi-function transaction cardin opposite directions), a pinching touch (e.g., a simultaneous touch tothe front side and the back side of the multi-function transactioncard), a rotating action (e.g., a rotating of the transaction card aboutan axis of the consumer multi-function transaction card), a bendingaction (e.g., a flexing of the consumer multi-function transaction cardperformed by applying force to opposite edges of the transaction card),and/or the like. The touch input may be a combination of inputs, such asa tapping, a pinching touch, and a swiping touch. The consumermulti-function transaction card may permit the consumer to define thetouch input that is used to trigger display of the optical pattern bythe multi-function transaction card.

In some implementations, the consumer input may be a movement input. Themovement input may relate to a movement of the consumer multi-functiontransaction card by the consumer. The consumer multi-functiontransaction card may sense the movement input using a sensor included inthe consumer multi-function transaction card, such as an accelerometer,a gyroscope, a motion sensor, and/or the like. The movement input may bea wave movement (e.g., a movement back-and-forth of the consumermulti-function transaction card in a waving motion), a tap movement(e.g., a movement of the consumer multi-function transaction cardtapping against a surface), a circular movement (e.g., a movement of theconsumer multi-function transaction card in a circular motion), and/orthe like. The consumer multi-function transaction card may permit theconsumer to define the movement input that is used to trigger display ofthe optical pattern by the multi-function transaction card.

In some implementations, the consumer input may be a touch input, amovement input, a combination of one or more touch inputs and/or one ormore movement inputs, and/or a sequence of one or more touch inputsand/or one or more movement inputs. The consumer input may be configuredby the issuer of the consumer multi-function transaction card. In someimplementations, the consumer may configure the consumer inputassociated with the consumer multi-function transaction card. Forexample, the consumer may configure a consumer input that is unique tothe consumer. The consumer multi-function transaction card may notdisplay the optical pattern unless the consumer multi-functiontransaction card senses the consumer input associated with consumermulti-function transaction card.

In some implementations, the consumer multi-function transaction cardmay be configured to display the optical pattern only when in thepresence of another device (e.g., a user device) associated with theconsumer. For example, the consumer multi-function transaction card maycommunicate with user device associated with the consumer. If theconsumer multi-function transaction card cannot communicate with theuser device associated with the consumer, does not sense the user deviceassociated with the consumer, is not in range of the user deviceassociated with the consumer, and/or the like, the consumermulti-function transaction card may be configured to not display theoptical pattern.

In this way, an unauthorized user of the consumer multi-functiontransaction card may not cause the consumer multi-function transactioncard to display the optical pattern. As such, the unauthorized user ofthe consumer multi-function transaction card may not authorize atransaction associated with the consumer multi-function transactioncard. Preventing an unauthorized user of the consumer multi-functiontransaction card from displaying the optical pattern identifiesfraudulent activity before a transaction is completed and conservescomputing resources that would have otherwise been used to complete thetransaction, identify the fraudulent activity, investigate thefraudulent activity, and/or report the fraudulent activity. The issuerassociated with the consumer multi-function transaction card and/or themerchant associated with the transaction may also conserve computingresources that would have otherwise been used to reverse the fraudulentactivity for the consumer, and/or identify, detect, and diagnose thefraudulent activity.

In some implementations, the consumer multi-function transaction cardmay display the optical pattern for a predetermined amount of time. Thepredetermined amount of time may be determined by the consumer, theissuer associated with the consumer multi-function transaction card, astandardized scheme (e.g., EMV), and/or the like. In someimplementations, the consumer multi-function transaction card maydisplay the optical pattern only when the consumer multi-functiontransaction card is physically located proximate to the terminal. Theconsumer multi-function transaction card may determine that the consumermulti-function transaction card is physically located proximate to theterminal based on the wireless connection (e.g., if the wirelessconnection is established then the consumer multi-function transactioncard is physically located proximate to the terminal), an NFC sensor,and/or the like. In some implementations, the consumer multi-functiontransaction card may stop displaying the optical pattern based onreceiving a consumer input. The consumer input may be the same as, orsimilar to, the consumer input described above with respect toinitiating the display of the optical pattern, described above.

In some implementations, the consumer multi-function transaction cardmay map aspects of the ARQC, the transaction information, informationassociated with the consumer multi-function transaction card,information associated with the consumer, information associated withthe issuer of the multi-function transaction card, and/or the like,within the optical pattern. In some implementations, certain aspects ofthe optical pattern may indicate certain aspects that can be used toquickly determine if the optical pattern is genuine or fraudulent. Forexample, the optical pattern may include portions (e.g., portions of amachine-readable code and/or a pattern of light) that indicateinformation transmitted from the terminal (e.g., the merchantmulti-function transaction card and/or the user device) to the consumermulti-function transaction card. The optical pattern may includeportions that indicate the full optical pattern (which can then be usedto compare against the optical pattern received by the terminal and/orthe transaction backend associated with the issuer of the consumermulti-function transaction card to ensure that the expected full opticalpattern matches the received full optical pattern). In someimplementations, the optical pattern may include portions that indicatedecrypted and/or secure information sent by the terminal and/or theissuer of the merchant multi-function transaction card and/or theconsumer multi-function transaction card (e.g., information that only agenuine consumer multi-function transaction card is capable ofdecrypting, based on the cryptographic key stored by the consumermulti-function transaction card), and/or the like. The terminal and/orthe transaction backend associated with the issuer of the merchantmulti-function transaction card and/or the consumer multi-functiontransaction card may identify fraudulent activity based on the mappedportions of the optical pattern as described herein. Identification offraudulent activity prior to completing the transaction conservescomputing resources that would have otherwise been used to complete thetransaction, identify the fraudulent activity, investigate thefraudulent activity, and/or report the fraudulent activity.

In some implementations, the consumer and/or the merchant multi-functiontransaction card may include a sensor. The sensor may be an image sensor(e.g., a sensor that is capable of capturing an image and/or detectingan image). In some implementations, that sensor may be a video sensor(e.g., a sensor that is capable of capturing a video). In someimplementations, the sensor may be a camera, such as amicroelectromechanical system (MEMS) camera, that is capable ofcapturing both images and video. In some implementations, the sensor mayinclude a photodiode.

As shown in FIG. 1C, and by reference numbers 114 and 116, the terminal(e.g., the merchant multi-function transaction card and/or user device)may receive the optical pattern by detecting, capturing, and/orrecording the optical pattern displayed by the consumer multi-functiontransaction card. For example, the merchant multi-function transactioncard may capture, detect, and/or record the optical pattern displayed bythe consumer multi-function transaction card using the sensor of themerchant multi-function transaction card. In some implementations, themerchant multi-function transaction card may scan the consumermulti-function transaction card to detect, capture, and/or record theoptical pattern. In some implementations, a user device associated withthe merchant may capture, detect, and/or record the optical patterndisplayed by the consumer multi-function transaction card using a sensorof the user device.

As shown by reference number 114, the merchant multi-functiontransaction card may detect and/or capture an image of the opticalpattern, such as the machine-readable code. The detected and/or capturedimage of the optical pattern may be stored by the merchantmulti-function transaction card.

As shown by reference number 116, the merchant multi-functiontransaction card may detect and/or record the optical pattern. Forexample, the merchant multi-function transaction card may detect and/orrecord the series of light pulses emitted by the output device of theconsumer multi-function transaction card. The series of light pulses maybe a series of pulses from different light sources, the same lightsource turning on and off in a pattern, one or more light sourcesvarying the color emitted by the one or more light sources, and/or thelike. For example, as discussed above, the light pattern may beassociated with VLC technology. The output device of the consumermulti-function transaction card may modulate light emitted based on aCSK scheme to transmit information. The sensor of the merchantmulti-function transaction card may detect, capture, and/or record thelight pattern emitted by the output device of the consumermulti-function transaction card. In some implementations, the lightpattern emitted by the output device of the consumer multi-functiontransaction card (or information derived from the light pattern) may bestored by the merchant multi-function transaction card.

In some implementations, the merchant multi-function transaction cardmay confirm that the optical pattern has been detected, captured, and/orrecorded. The merchant multi-function transaction card may provide anindication to the consumer multi-function transaction card and/or theuser device indicating whether the merchant multi-function transactioncard successfully detected, captured, and/or recorded the opticalpattern. In some implementations, the consumer and/or the merchantmulti-function transaction card may provide an indication to theconsumer and/or the merchant indicating whether the merchantmulti-function transaction card successfully detected, captured, and/orrecorded the optical pattern. For example, the output device of themerchant and/or the consumer multi-function transaction card may providean indication (such as a visual indication, such as a green light for asuccess and a red light for a failure) indicating whether the merchantmulti-function transaction card successfully detected, captured, and/orrecorded the optical pattern. Based on this indication, the merchantand/or the consumer may know that the attempt to detect, capture, and/orrecord the optical pattern failed and may use the merchant and/orconsumer multi-function transaction card to attempt to recapture,re-detect, and/or re-record the optical pattern.

As shown in FIG. 1D, and by reference number 118, the terminal (e.g.,the merchant multi-function transaction card and/or the user device) mayobtain the ARQC based on the optical pattern. The terminal may obtainthe ARQC by interpreting the optical pattern.

For example, the merchant multi-function transaction card may interpretthe optical pattern using one or more processors of the merchantmulti-function transaction card. The merchant multi-function transactioncard may process the multi-function transaction card using Reed-Solomonerror correction until the optical pattern can be appropriatelyinterpreted. The merchant multi-function transaction card may interpretthe optical pattern based on a standardized method associated with theoptical pattern. The obtained ARQC may be temporarily stored by themerchant multi-function transaction card. In some implementations, theARQC may not be stored at all by the merchant multi-function transactioncard.

In some implementations, the merchant multi-function transaction cardmay obtain additional information along with the ARQC. For example, theoptical pattern may include additional information that may be used todetermine the authenticity of the consumer multi-function transactioncard, the optical pattern, and/or the like, as described above. Themerchant multi-function transaction card may use this information todetermine if the consumer multi-function transaction card, the opticalpattern, and/or the like, are genuine. If the merchant multi-functiontransaction card determines that the consumer multi-function transactioncard, the optical pattern, and/or the like, are not genuine, themerchant multi-function transaction card may not proceed with completingthe transaction. If the merchant multi-function transaction carddetermines that the consumer multi-function transaction card, theoptical pattern, and/or the like, are not genuine, the merchantmulti-function transaction card may provide an indication to themerchant, such as by providing an indication using the output device ofthe merchant multi-function transaction card. Identifying a fraudulentconsumer multi-function transaction card, optical pattern, and/or thelike, by the merchant multi-function transaction card conservescomputing resources and/or network resources that would have otherwisebeen used to transmit the ARQC and complete the transaction, asdescribed herein.

In some implementations, the terminal (e.g., the merchant multi-functiontransaction card and/or the user device) may not be capable of accessingthe information contained in the ARQC. For example, the terminal may notbe capable of decrypting the ARQC. In some situations, the terminal maybe comprised (e.g., the merchant may be fraudulent, the terminal may befraudulent, the terminal may be comprised (e.g., by malware), and/or thelike). As such, by not allowing the terminal to access the informationcontained in the ARQC, the information contained in the ARQC isprotected, conserving computer resources and/or network resources thatwould have otherwise been used to identify, investigate, and/or correctfraudulent activity associated with a comprised terminal.

As shown by reference number 120, the terminal may transmit the ARQC. Insome implementations, the merchant multi-function transaction card maytransmit the ARQC to the user device associated with the merchant. Theuser device may transmit the ARQC to the transaction backend. In someimplementations, the merchant multi-function transaction card maytransmit the ARQC to the transaction backend.

In some implementations the terminal (e.g., the merchant multi-functiontransaction card and/or the user device) may transmit multiple ARQC'sassociated with one or more transactions to the transaction back end atthe same time. For example, the terminal may utilize batch processingfor transmitting the ARQC's. In some implementations, the terminal maytemporarily store ARQC's. The terminal may transmit the stored ARQC's atpredetermined time intervals. For example, the terminal may transmit allstored ARQC's once per hour, once per day, once per week, and/or thelike. In this way, the terminal may conserve computing and/or networkresources that would have otherwise been used to send each ARQCindividually.

The transaction backend may be associated with the issuer of themerchant multi-function transaction card and/or the consumermulti-function transaction card. The transaction backend may storetransaction account information (such as transaction account identifierinformation, consumer information, merchant information, deviceinformation, and/or the like) related to the issuer of the merchantmulti-function transaction card and/or the consumer multi-functiontransaction card. The transaction account information may be associatedwith an account corresponding to the consumer and/or the merchant.

The terminal (e.g., the merchant multi-function transaction card and/orthe user device) may communicate with the transaction backend. Theterminal may transmit the ARQC to the transaction backend associatedwith the issuer of the merchant multi-function transaction card and/orthe consumer multi-function transaction card. The ARQC may includeauthorization by the consumer for the transaction associated with theARQC. The transaction backend associated with the issuer of the merchantmulti-function transaction card and/or the consumer multi-functiontransaction card may confirm that ARQC is genuine (e.g., by decryptingthe ARQC, by checking the information within the ARQC, such asinformation associated with the consumer multi-function transactioncard, by checking one or more cryptographic keys associated with theARQC, and/or the like). The transaction backend associated with theissuer of the merchant multi-function transaction card and/or theconsumer multi-function transaction card may confirm the transactioninformation (e.g., confirm that a transaction account associated withthe consumer multi-function transaction card contains sufficientresources to complete the transaction, confirm the transaction accountassociated with the consumer multi-function transaction card is active,and/or the like). The transaction backend associated with the issuer ofthe merchant multi-function transaction card and/or the consumermulti-function transaction card may transmit a response code (e.g.,accepting or declining the transaction), an authorization responsecryptogram (ARPC) (the ARPC may be generated in a manner similar to thatas described herein with respect to the ARQC), and/or other informationrequired to complete the transaction. The transaction backend associatedwith the issuer of the merchant multi-function transaction card and/orthe consumer multi-function transaction card may perform the check ofthe ARQC, and the transaction information contained within the ARQC, inreal time. In some implementations, the transaction backend associatedwith the issuer of the merchant multi-function transaction card and/orthe consumer multi-function transaction card may perform the check inbatches containing one or more ARQC's.

In this way, the ARQC enables the transaction backend associated withthe issuer of the merchant multi-function transaction card and/or theconsumer multi-function transaction card to confirm that the consumermulti-function transaction card associated with the transaction isgenuine and that the transaction is capable of being executed. The ARQCallows for a cryptographic check that the consumer multi-functiontransaction card is genuine. Identifying a fraudulent consumermulti-function transaction card before completing the transactionconserves computing resources that would have otherwise been used by adevice associated with the consumer to complete the transaction,identify the fraudulent activity, investigate the fraudulent activity,and/or report the fraudulent activity. The issuer associated with theconsumer multi-function transaction card and/or the merchant associatedwith the transaction may also conserve computing resources that wouldhave otherwise been used to reverse the fraudulent activity for theconsumer, and/or identify, detect, and diagnose the fraudulent activity.

In some implementations, the terminal (e.g., the merchant multi-functiontransaction card and/or the user device) may provide a notificationindicating the response code (e.g., accepting or declining thetransaction). For example, the merchant multi-function transaction cardmay provide the notification using the output device of the merchantmulti-function transaction card.

By generating the optical pattern based on the ARQC, the consumermulti-function transaction card may reduce the risk of fraudulentactivity and conserve computing resources and/or network resources thatwould have otherwise been used to identify, investigate, and/or correctfraudulent activity. Additionally, or alternatively, the consumermulti-function transaction card may authorize payments without the useof a near-field communication (NFC) chip, which may reduce a cost ofmanufacturing of the multi-function transaction card and/or permit themulti-function transaction card to authorize payments when an NFC chipis not working, the terminal does not have an NFC chip, and/or the like.

In some implementations, the merchant multi-function transaction cardmay be capable of performing one or more (or all) of the functionsdescribed herein with respect to the consumer multi-function transactioncard, or vice versa. In some implementations, the merchantmulti-function transaction card may be capable of performing one or morefunctions which is not capable of being performed by the consumermulti-function transaction card, or vice versa. In some implementations,the user device associated with the merchant may be capable ofperforming one or more (or all) of the functions described herein withrespect to the merchant multi-function transaction card, and vice versa.

As indicated above, FIGS. 1A-1D are provided as one or more examples.Other examples may differ from what is described with regard to FIGS.1A-1D. The number and arrangement of devices shown in FIGS. 1A-1D areprovided as one or more examples. In practice, there may be additionaldevices, fewer devices, different devices, or differently arrangeddevices than those shown in FIGS. 1A-1D. Furthermore, two or moredevices shown in FIGS. 1A-1D may be implemented within a single device,or a single device shown in FIGS. 1A-1D may be implemented as multiple,distributed devices. Additionally, or alternatively, a set of devices(e.g., one or more device) of FIGS. 1A-1D may perform one or morefunctions described as being performed by another set of devices ofFIGS. 1A-1D.

FIG. 2 is a diagram of an example environment 200 in which systems,devices, and/or methods, described herein, may be implemented. As shownin FIG. 2 , environment 200 may include a merchant multi-functiontransaction card 210, a transaction terminal 220, a user device 230, anetwork 240, a transaction backend 250, and a consumer multi-functiontransaction card 260. Devices of environment 200 may interconnect viawired connections, wireless connections, or a combination of wired andwireless connections.

Merchant multi-function transaction card 210 includes a transaction cardcapable of storing and/or communicating data for a PoS transaction withtransaction terminal 220 and/or consumer multi-function transaction card260. For example, merchant multi-function transaction card 210 may storeor communicate data including account information (e.g., an accountidentifier, a cardholder identifier, etc.), expiration information ofmerchant multi-function transaction card 210, banking information,transaction information (e.g., a payment token), and/or the like. Forexample, to store or communicate the data, merchant multi-functiontransaction card 210 may include a magnetic stripe and/or an IC chip(e.g., an EMV chip and/or the like).

In some implementations, merchant multi-function transaction card 210may include an antenna to communicate data associated with merchantmulti-function transaction card 210. The antenna may be a passive radiofrequency (RF) antenna, an active RF antenna, and/or a battery-assistedRF antenna. In some implementations, merchant multi-function transactioncard 210 may be a smart transaction card, capable of communicatingwirelessly (e.g., via Bluetooth, Bluetooth Low Energy (BLE), near-fieldcommunication (NFC), and/or the like) with a computing device, such astransaction terminal 220 and/or consumer multi-function transaction card260, a digital wallet, and/or another device. In some implementations,merchant multi-function transaction card 210 may communicate withtransaction terminal 220 and/or consumer multi-function transaction card260 to complete a transaction (e.g., based on being moved withincommunicative proximity of transaction terminal 220 and/or consumermulti-function transaction card 260).

Transaction terminal 220 includes one or more devices to facilitateprocessing a transaction via merchant multi-function transaction card210 and/or consumer multi-function transaction card 260. Transactionterminal 220 may include a PoS terminal, a security access terminal, anATM terminal, a multi-function transaction card (e.g., merchantmulti-function transaction card 210), a user device (e.g., user device230), and/or the like. Transaction terminal 220 may include one or moreinput devices and/or output devices to facilitate obtaining transactioncard data from merchant multi-function transaction card 210 and/orconsumer multi-function transaction card 260, and/or interaction orauthorization from a cardholder of merchant multi-function transactioncard 210 and/or consumer multi-function transaction card 260. Exampleinput devices of transaction terminal 220 may include a number keypad, atouchscreen, a magnetic stripe reader, a chip reader, and/or an RFsignal reader. A magnetic stripe reader of transaction terminal 220 mayreceive transaction card data as a magnetic stripe of merchantmulti-function transaction card 210 and/or consumer multi-functiontransaction card 260 is swiped along the magnetic stripe reader. A chipreader of transaction terminal 220 may receive transaction card datafrom an IC chip (e.g., an EMV chip) of merchant multi-functiontransaction card 210 and/or consumer multi-function transaction card 260when the chip is placed in contact with the chip reader. An RF signalreader of transaction terminal 220 may enable contactless transactionsfrom merchant multi-function transaction card 210 and/or consumermulti-function transaction card 260 by obtaining transaction card datawirelessly from merchant multi-function transaction card 210 and/orconsumer multi-function transaction card 260 as merchant multi-functiontransaction card 210 and/or consumer multi-function transaction card 260comes within a range of transaction terminal 220 at which the RF signalreader may detect an RF signal from an RF antenna of merchantmulti-function transaction card 210 and/or consumer multi-functiontransaction card 260. Example output devices of transaction terminal 220may include a display device, a speaker, a printer, and/or the like.

User device 230 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith merchant multi-function transaction card 210 and/or consumermulti-function transaction card 260. For example, user device 230 mayinclude a communication device and/or a computing device, such as amobile phone (e.g., a smart phone, a radiotelephone, etc.), a desktopcomputer, a laptop computer, a tablet computer, a handheld computer, agaming device, a wearable communication device (e.g., a smartwristwatch, a pair of smart eyeglasses, etc.), or a similar type ofdevice. In some implementations, user device 230 may include applicationlogic capable of facilitating communications between transactionterminal 220 and consumer multi-function transaction card 260.

Network 240 includes one or more wired and/or wireless networks. Forexample, network 240 may include a cellular network (e.g., a long-termevolution (LTE) network, a code division multiple access (CDMA) network,a 3G network, a 4G network, a 5G network, another type of nextgeneration network, etc.), a public land mobile network (PLMN), a localarea network (LAN), a wide area network (WAN), a metropolitan areanetwork (MAN), a telephone network (e.g., the Public Switched TelephoneNetwork (PSTN)), a private network, an ad hoc network, an intranet, theInternet, a fiber optic-based network, a cloud computing network, and/orthe like, and/or a combination of these or other types of networks.

Transaction backend 250 includes one or more devices associated withbanks and/or transaction card associations that authorize transactionsand/or facilitate a transfer of funds or payments between an account ofa cardholder of merchant multi-function transaction card 210 and/orconsumer multi-function transaction card 260 and an account of anindividual or business of transaction terminal 220. For example,transaction backend 250 may include one or more devices of one or moreissuing banks associated with a cardholder of merchant multi-functiontransaction card 210 and/or consumer multi-function transaction card260, one or more devices of one or more acquiring banks (or merchantbanks) associated with transaction terminal 220, and/or one or moredevices associated with one or more card associations (e.g., VISA®,MASTERCARD®, and/or the like) associated with merchant multi-functiontransaction card 210 and/or consumer multi-function transaction card260. Accordingly, in response to receiving transaction card dataassociated with merchant multi-function transaction card 210 and/orconsumer multi-function transaction card 260 from transaction terminal220, various banking institutions and/or card associations oftransaction backend 250 may communicate to authorize the transactionand/or transfer funds between the accounts associated with merchantmulti-function transaction card 210, consumer multi-function transactioncard 260, and/or transaction terminal 220.

In some implementations, transaction backend 250 may include one or moredevices associated with security that may provide or deny authorizationassociated with transactions. For example, transaction backend 250 maystore and/or provide security access information that may or may notallow access through an access point (e.g., a gate, a door, and/or thelike) of a secure location (e.g., a room, a building, an geographicalarea, a transportation terminal, and/or the like) based on information(e.g., account information, a key, an identifier, credentials, and/orthe like) associated with merchant multi-function transaction card 210and/or consumer multi-function transaction card 260 and/or provided bytransaction terminal 220.

In some implementations, transaction backend 250 may include one or moredevices associated with a rewards program relating to merchantmulti-function transaction card 210, consumer multi-function transactioncard 260, and/or an entity (e.g., a bank, a merchant, a serviceprovider, a vendor, and/or the like) associated with merchantmulti-function transaction card 210, consumer multi-function transactioncard 260, and/or transaction terminal 220. For example, transactionbackend 250 may authorize the earning and/or redemption of rewards(e.g., rewards points associated with merchant multi-functiontransaction card 210 and/or consumer multi-function transaction card260, cash rewards, client loyalty rewards associated with an entityassociated with transaction terminal 220, and/or the like) based on atransaction processed by transaction terminal 220 with merchantmulti-function transaction card 210 and/or consumer multi-functiontransaction card 260.

Consumer multi-function transaction card 260 includes a transaction cardcapable of storing and/or communicating data for a PoS transaction withtransaction terminal 220, and capable of receiving and/or storing datafor a PoS transaction with merchant multi-function transaction card 210.For example, consumer multi-function transaction card 260 may store orcommunicate data including account information (e.g., an accountidentifier, a cardholder identifier, etc.), expiration information ofconsumer multi-function transaction card 260, banking information,transaction information (e.g., a payment token), and/or the like. Forexample, to store or communicate the data, consumer multi-functiontransaction card 260 may include a magnetic stripe and/or an IC chip(e.g., an EMV chip and/or the like).

In some implementations, consumer multi-function transaction card 260may include a card body in or on which various components are embedded.In some implementations, consumer multi-function transaction card 260may include an antenna to communicate data associated with transactionterminal 220 and/or merchant multi-function transaction card 210. Theantenna may be a passive RF antenna, an active RF antenna, and/or abattery-assisted RF antenna. In some implementations, consumermulti-function transaction card 260 may be a smart transaction card,capable of communicating wirelessly (e.g., via Bluetooth, BLE, NFC,and/or the like) with a computing device, such as transaction terminal220, merchant multi-function transaction card 210, a digital wallet,and/or another device. In some implementations, consumer multi-functiontransaction card 260 may communicate with transaction terminal 220,merchant multi-function transaction card 210, and/or the like tocomplete a transaction (e.g., based on being moved within communicativeproximity of transaction terminal 220, merchant multi-functiontransaction card 210, and/or the like). In some implementations,consumer multi-function transaction card 260 may include one or morecomponents and/or one or more functionalities of transaction terminal220 and/or one or more components and/or functionalities of merchantmulti-function transaction card 210.

Power bus 262 includes a component that permits the delivery of power tovarious components of consumer multi-function transaction card 260. Bus264 includes a component (e.g., a serial communication bus, such as aserial peripheral interface (SPI) bus, a universal asynchronousreceiver-transmitter (UART)-based bus, a bus based on theinter-integrated circuit (I2C) protocol, and/or the like) that permitscommunication among various components of consumer multi-functiontransaction card 260. RF/NFC 266 may include a communication link thatpermits data delivery between secure element 274, NFC antenna 276, andNFC front end 278.

Power source 268 includes one or more devices, internal to consumermulti-function transaction card 260, capable of supplying power. Forexample, power source 268 may include a battery (e.g., a rechargeablebattery, a non-rechargeable battery, and/or the like), a power supply, acapacitor (e.g., a supercapacitor, an ultracapacitor, and/or the like),and/or the like. In some implementations, consumer multi-functiontransaction card 260 (e.g., controller 272, secure element 274, and/orNFC front end 278) may obtain power from power source 268 when consumermulti-function transaction card 260 is to perform a transaction. In someaspects, consumer multi-function transaction card 260 may include asingle power source 268, which may supply power for performing atransaction and/or may supply power to one or more other components ofconsumer multi-function transaction card 260 (e.g., a processor, astorage component, an input component, an output component, acommunication interface, and/or the like). In some aspects, consumermulti-function transaction card 260 may include multiple power sources268. In some aspects, a single power source 268 may be dedicated tosupplying power solely for performing a transaction, while other powersources 268 may supply power to other components of consumermulti-function transaction card 260. In some implementations, consumermulti-function transaction card 260 may include one or more solar cellsand associated circuitry that enable various components of consumermulti-function transaction card 260 to be powered by solar energy.

Power management component 270 includes one or more devices capable ofcontrolling the delivery of power to various components of consumermulti-function transaction card 260 and/or controlling charging of powersource 268. For example, power management component 270 may include aswitch, a gate, a controller, a regulator, a processing component,and/or the like. In some implementations, power management component 270may include a bidirectional logic level shifter to control signalsbetween controller 272 and secure element 274 (e.g., to couple ordecouple controller 272 and secure element 274, to prevent signals frombeing passed between controller 272 and secure element 274, and/or thelike). Additionally, or alternatively, power management component 270may include a diode (e.g., an ideal diode) and/or a switch (e.g., a loadswitch) to control signals between power source 268 and secure element274 (e.g., to couple or decouple power source 268 and secure element274, to prevent signals from being passed between power source 268 andsecure element 274, and/or the like).

Controller 272 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information and/orinstructions that assist with performing a transaction. For example,controller 272 may include a processor, such as processor 320 describedbelow in connection with FIG. 3 . Additionally, or alternatively,controller 272 may include memory, such as memory 330 described below inconnection with FIG. 3 . In some implementations, controller 272 may bedirectly, communicatively coupled to secure element 274 (e.g., via adedicated, single-wire communication link).

Secure element 274 includes one or more devices capable of securelyhosting an operating system and/or an application, and/or storingconfidential information (e.g., a credential, cryptographic information,and/or the like). For example, secure element 274 may include auniversal integrated circuit card (UICC), a secure digital (SD) card(e.g., a microSD card and/or the like), an embedded secure element,and/or the like. In some implementations, secure element 274 may includea tamper resistant hardware platform. In some implementations, secureelement 274 may include one or more processors (e.g., one or moremicrocontrollers) certified by a standard body group, such as an EMVConsortium (EMVCo) certified (e.g., 16-bit and/or the like) securemicrocontroller.

In some implementations, secure element 274 may host a personalized cardapplication and a cryptographic key required to perform a financialtransaction (e.g., with transaction terminal 220). In someimplementations, secure element 274 may receive a cryptographic keyrequired to perform a financial transaction (e.g., with merchantmulti-function transaction card 210), as described elsewhere herein. Insome implementations, secure element 274 may store a credentialassociated with consumer multi-function transaction card 260, such as ausername, a password, biometric information, a token, a certificate forsigning documents, and/or the like. In some implementations, secureelement 274 may store a credential (e.g., a username, a password,biometric information, a token, a certificate for signing documents,and/or the like) associated with another transaction card (e.g.,merchant multi-function transaction card 210), as described elsewhereherein.

In some implementations, secure element 274 may include applicationlogic configured to communicate with NFC front end 278 (e.g., to causeNFC front end 278 to provide card data from secure element 274 totransaction terminal 220 to submit a payment, to cause NFC front end 278to receive card data from another transaction card (e.g., merchantmulti-function transaction card 210) to process a payment, and/or thelike). In some implementations, secure element 274 may includeapplication logic configured to communicate with controller 272 (e.g.,to cause controller 272 to communicate with a user device (e.g., userdevice 230) to facilitate online data authentication relating to atransaction (e.g., with merchant multi-function transaction card 210),to receive instructions from controller 272 to initiate transactionprocessing (e.g., associated with merchant multi-function transactioncard 210), and/or the like). In some implementations, secure element 274may include application logic configured to receive inputs from inputdevice 280 (e.g., directly or via controller 272), to provide outputs tooutput device 282 (e.g., directly or via controller 272), and/or thelike.

NFC antenna 276 includes an antenna capable of transmitting and/orreceiving information using an NFC protocol. For example, NFC antenna276 may include a loop antenna (e.g., an NFC loop antenna), an inductor(e.g., an NFC inductor), and/or the like. In some implementations, NFCantenna 276 may be integrated into, or with, secure element 274 and/orNFC front end 278 (e.g., may be part of the same integrated circuit,such as a transaction IC).

NFC front end 278 includes one or more devices capable of communicatingwith external devices, such as merchant multi-function transaction card210 and/or transaction terminal 220, using an NFC protocol. NFC frontend 278 may be communicatively coupled to secure element 274, andconfigured to obtain card data from secure element 274 and provide thecard data to transaction terminal 220, as described elsewhere herein. Insome implementations, NFC front end 278 may be configured to receivecard data from merchant multi-function transaction card 210 and providethe card data to secure element 274 for processing, as describedelsewhere herein.

NFC front end 278 may include one or more radio modules for receivingand/or emitting NFC signals. NFC front end 278 may include one or moreprocessors (e.g., microprocessor(s), microcontroller(s), and/or thelike) and/or be coupled to one or more processors, such as controller272, processor(s) included in secure element 274, and/or the like.

Although not shown, in some implementations, consumer multi-functiontransaction card 260 may include a transaction IC that includes anintegrated circuit connecting secure element 274, NFC antenna 276,and/or one or more other components of consumer multi-functiontransaction card 260. For example, the transaction IC may include secureelement 274, NFC antenna 276, NFC front end 278, connection(s) betweensecure element 274, NFC antenna 276, and NFC front end 278, and/or thelike.

Input device 280 includes one or more components that permit consumermulti-function transaction card 260 to receive information, such as viauser input (e.g., to initiate a transaction, such as to receive carddata from merchant multi-function transaction card 210). For example,input device 280 may include an input component, such as input componentdescribed below in connection with FIG. 3 . For example, input device280 may include an accelerometer, pushbutton(s), touch sensor(s), keypadinput(s), a camera, and/or the like.

Output device 282 includes one or more components that permit consumermulti-function transaction card 260 to provide output information (e.g.,relating to transaction processing associated with merchantmulti-function transaction card 210 and/or transaction terminal 220).For example, output device 282 may include an output component, such asoutput component 360 described below in connection with FIG. 3 . Forexample, output device 282 may include dot matrix display(s), one ormore LEDs (e.g., printed organic LEDs), and/or the like.

Communication device 284 includes a transceiver-like component thatenables consumer multi-function transaction card 260 to communicate withother devices. For example, communication device 284 may include acommunication interface, such as communication interface 370 describedbelow in connection with FIG. 3 . In some implementations, communicationdevice 284 may include a Bluetooth communication interface, a BLEcommunication interface, and/or the like. In some implementations,communication device 284 may be included in, or integrated with,controller 272.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2 . Furthermore, two or more devices shown in FIG. 2 maybe implemented within a single device, or a single device shown in FIG.2 may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 may perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to merchant multi-function transaction card 210,transaction terminal 220, user device 230, transaction backend 250,and/or consumer multi-function transaction card 260. In someimplementations, merchant multi-function transaction card 210,transaction terminal 220, user device 230, transaction backend 250,and/or consumer multi-function transaction card 260 may include one ormore devices 300 and/or one or more components of device 300. As shownin FIG. 3 , device 300 may include a bus 310, a processor 320, a memory330, a storage component 340, an input component 350, an outputcomponent 360, and a communication interface 370.

Bus 310 includes a component that permits communication among multiplecomponents of device 300. Processor 320 is implemented in hardware,firmware, and/or a combination of hardware and software. Processor 320is a central processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 320includes one or more processors capable of being programmed to perform afunction. Memory 330 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, and/or amagneto-optic disk), a solid state drive (SSD), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 mayinclude a component for determining location (e.g., a global positioningsystem (GPS) component) and/or a sensor (e.g., an accelerometer, agyroscope, an actuator, another type of positional or environmentalsensor, and/or the like). Output component 360 includes a component thatprovides output information from device 300 (via, e.g., a display, aspeaker, a haptic feedback component, an audio or visual indicator,and/or the like).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver, a separate receiver, a separate transmitter, and/or thelike) that enables device 300 to communicate with other devices, such asvia a wired connection, a wireless connection, or a combination of wiredand wireless connections. Communication interface 370 may permit device300 to receive information from another device and/or provideinformation to another device. For example, communication interface 370may include an Ethernet interface, an optical interface, a coaxialinterface, an infrared interface, a radio frequency (RF) interface, auniversal serial bus (USB) interface, a Wi-Fi interface, a cellularnetwork interface, and/or the like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes based on processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. As used herein,the term “computer-readable medium” refers to a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardware circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3 . Additionally, or alternatively,a set of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for authorizing apayment with a multi-function transaction card. In some implementations,one or more process blocks of FIG. 4 may be performed by amulti-function transaction card (e.g., merchant multi-functiontransaction card 210 and/or consumer multi-function transaction card260) having a card body having dimensions that are in accordance with astandard for transaction cards, an output device on the card body, asecure element within the card body, one or more memories within thecard body, and/or one or more processors within the card body, whereinthe one or more processors are communicatively coupled to the one ormore memories. In some implementations, one or more process blocks ofFIG. 4 may be performed by another device or a group of devices separatefrom or including the multi-function transaction card, such as atransaction terminal (e.g., transaction terminal 220), a user device(e.g., user device 230), a transaction backend (e.g., transactionbackend 250), and/or the like.

As shown in FIG. 4 , process 400 may include pairing, via a wirelessconnection, the multi-function transaction card with a terminal (block410). For example, the multi-function transaction card (e.g., usingprocessor 320, memory 330, storage component 340, input component 350,output component 360, communication interface 370, and/or the like) maypair, via a wireless connection, the multi-function transaction cardwith a terminal, as described above.

As further shown in FIG. 4 , process 400 may include receiving, from theterminal, information associated with a transaction (block 420). Forexample, the multi-function transaction card (e.g., using processor 320,memory 330, storage component 340, input component 350, output component360, communication interface 370, and/or the like) may receive, from theterminal, information associated with a transaction, as described above.

As further shown in FIG. 4 , process 400 may include generating, basedon the information associated with the transaction, and using acryptographic key, an authorization request cryptogram (ARQC), whereinthe cryptographic key is stored in the secure element (block 430). Forexample, the multi-function transaction card (e.g., using processor 320,memory 330, storage component 340, input component 350, output component360, communication interface 370, and/or the like) may generate, basedon the information associated with the transaction, and using acryptographic key, an authorization request cryptogram (ARQC), asdescribed above. In some implementations, the cryptographic key isstored in the secure element.

As further shown in FIG. 4 , process 400 may include generating, basedon the ARQC, a machine-readable code (block 440). For example, themulti-function transaction card (e.g., using processor 320, memory 330,storage component 340, input component 350, output component 360,communication interface 370, and/or the like) may generate, based on theARQC, a machine-readable code, as described above.

As further shown in FIG. 4 , process 400 may include displaying, usingthe output device, the machine-readable code (block 450). For example,the multi-function transaction card (e.g., using processor 320, memory330, storage component 340, input component 350, output component 360,communication interface 370 and/or the like) may display, using theoutput device, the machine-readable code, as described above.

Process 400 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In a first implementation, the one or more processors are configured to,when receiving, from the terminal, the information associated with thetransaction, receive, from the terminal, the information associated withthe transaction via the wireless connection.

In a second implementation, alone or in combination with the firstimplementation, the wireless connection comprises at least one of aBluetooth connection or near-field communication connection.

In a third implementation, alone or in combination with one or more ofthe first and second implementations, the information associated withthe transaction comprises an amount of the transaction.

In a fourth implementation, alone or in combination with one or more ofthe first through third implementations, the terminal comprises anothermulti-function transaction card, and the other multi-functiontransaction card comprises an image sensor for capturing an image of themachine-readable code.

In a fifth implementation, alone or in combination with one or more ofthe first through fourth implementations, the output device comprises atleast one of a dot matrix display, an electronic ink display, or alight-emitting-diode display.

In a sixth implementation, alone or in combination with one or more ofthe first through fifth implementations, the machine-readable codecomprises at least one of a Quick Response code, a matrix barcode, or aone-dimensional barcode.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4 . Additionally, or alternatively, two or more of theblocks of process 400 may be performed in parallel.

FIG. 5 is a flow chart of an example process 500 for authorizing apayment with a multi-function transaction card. In some implementations,one or more process blocks of FIG. 5 may be performed by amulti-function transaction card (e.g., merchant multi-functiontransaction card 210 and/or consumer multi-function transaction card260). In some implementations, one or more process blocks of FIG. 5 maybe performed by another device or a group of devices separate from orincluding the multi-function transaction card, such as a transactionterminal (e.g., transaction terminal 220), a user device (e.g., userdevice 230), a transaction backend (e.g., transaction backend 250),and/or the like.

As shown in FIG. 5 , process 500 may include receiving, from a terminal,information associated with a transaction, wherein the multi-functiontransaction card has dimensions that are in accordance with a standardfor transaction cards (block 510). For example, the multi-functiontransaction card (e.g., using processor 320, memory 330, storagecomponent 340, input component 350, output component 360, communicationinterface 370, and/or the like) may receive, from a terminal,information associated with a transaction, as described above. In someimplementations, the multi-function transaction card has dimensions thatare in accordance with a standard for transaction cards.

As further shown in FIG. 5 , process 500 may include generating based onthe information associated with the transaction, and using acryptographic key, an authorization request cryptogram (ARQC), whereinthe cryptographic key is stored in a secure element, and wherein themulti-function transaction card comprises the secure element (block520). For example, the multi-function transaction card (e.g., usingprocessor 320, memory 330, storage component 340, input component 350,output component 360, communication interface 370, and/or the like) maygenerate based on the information associated with the transaction, andusing a cryptographic key, an authorization request cryptogram (ARQC),as described above. In some implementations, the cryptographic key isstored in a secure element. In some implementations, the multi-functiontransaction card comprises the secure element.

As further shown in FIG. 5 , process 500 may include generating, basedon the ARQC, an optical pattern (block 530). For example, themulti-function transaction card (e.g., using processor 320, memory 330,storage component 340, input component 350, output component 360,communication interface 370, and/or the like) may generate, based on theARQC, an optical pattern, as described above.

As further shown in FIG. 5 , process 500 may include outputting, usingan output device, the optical pattern (block 540). For example, themulti-function transaction card (e.g., using processor 320, memory 330,storage component 340, input component 350, output component 360,communication interface 370, and/or the like) may output, using anoutput device, the optical pattern, as described above.

Process 500 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In a first implementation, receiving, from the terminal, the informationassociated with the transaction comprises receiving, from the terminal,the information associated with the transaction via a wirelessconnection.

In a second implementation, alone or in combination with the firstimplementation, the wireless connection comprises at least one of aBluetooth connection or near-field communication connection.

In a third implementation, alone or in combination with one or more ofthe first and second implementations, the multi-function transactioncard is a first multi-function transaction card, the terminal comprisesa second multi-function transaction card, and the second multi-functiontransaction card comprises a sensor for receiving the optical pattern.

In a fourth implementation, alone or in combination with one or more ofthe first through third implementations, the terminal is a mobiledevice.

In a fifth implementation, alone or in combination with one or more ofthe first through fourth implementations, the optical pattern comprisesa machine-readable code, and outputting the optical pattern comprisesdisplaying, using the output device, the machine-readable code.

In a sixth implementation, alone or in combination with one or more ofthe first through fifth implementations, the optical pattern comprises apulsed light pattern, and outputting the optical pattern comprisesemitting, using the output device and based on the pulsed light pattern,a series of light pulses.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5 . Additionally, or alternatively, two or more of theblocks of process 500 may be performed in parallel.

FIG. 6 is a flow chart of an example process 600 for authorizing apayment with a multi-function transaction card. In some implementations,one or more process blocks of FIG. 6 may be performed by amulti-function transaction card (e.g., merchant multi-functiontransaction card 210 and/or consumer multi-function transaction card260). In some implementations, one or more process blocks of FIG. 6 maybe performed by another device or a group of devices separate from orincluding the multi-function transaction card, such as a transactionterminal (e.g., transaction terminal 220), a user device (e.g., userdevice 230), a transaction backend (e.g., transaction backend 250),and/or the like.

As shown in FIG. 6 , process 600 may include pairing, via a wirelessconnection, a multi-function transaction card with a terminal (block610). For example, the multi-function transaction card (e.g., usingprocessor 320, memory 330, storage component 340, input component 350,output component 360, communication interface 370, and/or the like) maypair, via a wireless connection, a multi-function transaction card witha terminal, as described above.

As further shown in FIG. 6 , process 600 may include receiving, from theterminal, information associated with a transaction (block 620). Forexample, the multi-function transaction card (e.g., using processor 320,memory 330, storage component 340, input component 350, output component360, communication interface 370, and/or the like) may receive, from theterminal, information associated with a transaction, as described above.

As further shown in FIG. 6 , process 600 may include generating, basedon the information associated with the transaction and using acryptographic key, an authorization request cryptogram (ARQC), whereinthe cryptographic key is stored in a secure element in themulti-function transaction card (block 630). For example, themulti-function transaction card (e.g., using processor 320, memory 330,storage component 340, input component 350, output component 360,communication interface 370, and/or the like) may generate, based on theinformation associated with the transaction and using a cryptographickey, an authorization request cryptogram (ARQC), as described above. Insome implementations, the cryptographic key is stored in a secureelement in the multi-function transaction card.

As further shown in FIG. 6 , process 600 may include generating, basedon the ARQC, a pulsed light pattern (block 640). For example, themulti-function transaction card (e.g., using processor 320, memory 330,storage component 340, input component 350, output component 360,communication interface 370, and/or the like) may generate, based on theARQC, a pulsed light pattern, as described above.

As further shown in FIG. 6 , process 600 may include causing an outputdevice of the multi-function transaction card to emit, based on thepulsed light pattern, a series of light pulses (block 650). For example,the multi-function transaction card (e.g., using processor 320, memory330, storage component 340, input component 350, output component 360,communication interface 370, and/or the like) may cause an output deviceof the multi-function transaction card to emit, based on the pulsedlight pattern, a series of light pulses, as described above.

Process 600 may include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In a first implementation, the one or more instructions, that cause theone or more processors to receive, from the terminal, the informationassociated with the transaction, cause the one or more processors toreceive, from the terminal, the information associated with thetransaction via the wireless connection.

In a second implementation, alone or in combination with the firstimplementation, the wireless connection comprises at least one of aBluetooth connection or near-field communication connection.

In a third implementation, alone or in combination with one or more ofthe first and second implementations, the terminal comprises anothermulti-function transaction card, and the other multi-functiontransaction card comprises, for receiving the series of light pulses, atleast one of an image sensor or a light sensor.

In a fourth implementation, alone or in combination with one or more ofthe first through third implementations, the output device comprises aplurality of light-emitting-diodes, and the one or more instructions,that cause the one or more processors to cause the output device to emitthe series of light pulses, cause the one or more processors to causethe output device to illuminate, based on the series of light pulses,one or more of the plurality of light-emitting-diodes.

In a fifth implementation, alone or in combination with one or more ofthe first through fourth implementations, the one or more instructions,that cause the one or more processors to cause the output device to emitthe series of light pulses, cause the one or more processors to causethe output device to emit, using pulse-width modulation, the series oflight pulses.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6 . Additionally, or alternatively, two or more of theblocks of process 600 may be performed in parallel.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations may be made inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Certain user interfaces have been described herein and/or shown in thefigures. A user interface may include a graphical user interface, anon-graphical user interface, a text-based user interface, and/or thelike. A user interface may provide information for display. In someimplementations, a user may interact with the information, such as byproviding input via an input component of a device that provides theuser interface for display. In some implementations, a user interfacemay be configurable by a device and/or a user (e.g., a user may changethe size of the user interface, information provided via the userinterface, a position of information provided via the user interface,etc.). Additionally, or alternatively, a user interface may bepre-configured to a standard configuration, a specific configurationbased on a type of device on which the user interface is displayed,and/or a set of configurations based on capabilities and/orspecifications associated with a device on which the user interface isdisplayed.

It will be apparent that systems and/or methods described herein may beimplemented in different forms of hardware, firmware, or a combinationof hardware and software. The actual specialized control hardware orsoftware code used to implement these systems and/or methods is notlimiting of the implementations. Thus, the operation and behavior of thesystems and/or methods are described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterm “set” is intended to include one or more items (e.g., relateditems, unrelated items, a combination of related and unrelated items,etc.), and may be used interchangeably with “one or more.” Where onlyone item is intended, the phrase “only one” or similar language is used.Also, as used herein, the terms “has,” “have,” “having,” or the like areintended to be open-ended terms. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise. Also, as used herein, the term “or” is intended to beinclusive when used in a series and may be used interchangeably with“and/or,” unless explicitly stated otherwise (e.g., if used incombination with “either” or “only one of”).

What is claimed is:
 1. A method, comprising: receiving, by a mobiledevice, first information from a merchant multi-function transactioncard, wherein the mobile device is a consumer multi-function transactioncard of a consumer; identifying, by the mobile device, a cryptogrambased on receiving the first information from the merchantmulti-function transaction card; generating, by the mobile device, alight pattern based on the cryptogram; and providing, by the mobiledevice and for display, second information based on the light patternand only after the mobile device senses a consumer input of theconsumer, wherein the consumer input is a sequence, unique to theconsumer, and associated with the mobile device, and wherein thesequence includes: a touch input that relates to an amount of time thatthe consumer remained in contact with the consumer multi-functiontransaction card, and a movement input by the consumer moving theconsumer multi-function transaction card in a particular motion.
 2. Themethod of claim 1, wherein the first information includes transactioninformation associated with a transaction.
 3. The method of claim 1,wherein the cryptogram is identified further based on a card key storedby a secure element of the mobile device.
 4. The method of claim 1,wherein providing the second information comprises: providing an opticalpattern as a combination of a machine-readable code and the lightpattern.
 5. The method of claim 4, wherein the machine-readable codeincludes a first portion of the second information, and wherein thelight pattern includes a second portion of the second information. 6.The method of claim 1, wherein the second information is provided onlywhen the mobile device is in presence of a device associated with theconsumer, and wherein the device associated with the consumer is a userdevice.
 7. The method of claim 1, wherein the second information isprovided only when the mobile device is physically located proximate toa terminal associated with the first information based on a near-fieldcommunication (NFC) sensor.
 8. The method of claim 1, wherein thesequence further includes one or more of: a tapping by the consumer onthe consumer multi-function transaction card, a pinching touch by theconsumer on the consumer multi-function transaction card, or a swipingtouch by the consumer on the consumer multi-function transaction card.9. The method of claim 1, wherein the particular motion comprises awaving motion.
 10. The method of claim 1, wherein the touch inputcomprises a flexing of the consumer multi-function transaction cardperformed by applying force to one or more edges of the consumermulti-function transaction card.
 11. A mobile device, comprising: one ormore memories; and one or more processors, communicatively coupled tothe one or more memories, configured to: receive first information froma merchant multi-function transaction card, wherein the mobile device isa consumer multi-function transaction card of a consumer; identify acryptogram based on receiving the first information from the merchantmulti-function transaction card; generate a light pattern based on thecryptogram; and provide, for display, second information based on thelight pattern and only after the mobile device senses a consumer inputof the consumer, wherein the consumer input is a sequence, unique to theconsumer, and associated with the mobile device, and wherein thesequence includes: a touch input that relates to an amount of time thatthe consumer remained in contact with the consumer multi-functiontransaction card, and a movement input by the consumer moving theconsumer multi-function transaction card in a particular motion.
 12. Themobile device of claim 11, wherein the first information includestransaction information associated with a transaction.
 13. The mobiledevice of claim 11, wherein the cryptogram is identified further basedon a card key stored by a secure element of the mobile device.
 14. Themobile device of claim 11, wherein the one or more processors, whenproviding the second information, are configured to: provide an opticalpattern as a combination of a machine-readable code and the lightpattern.
 15. The mobile device of claim 11, wherein the secondinformation is provided only when the mobile device is in presence of adevice associated with the consumer.
 16. The mobile device of claim 11,wherein the second information is provided only when the mobile deviceis physically located proximate to a terminal associated with the firstinformation based on a near-field communication (NFC) sensor.
 17. Anon-transitory computer-readable medium storing a set of instructions,the set of instructions comprising: one or more instructions that, whenexecuted by one or more processors of a consumer multi-functiontransaction card of a consumer, cause the consumer multi-functiontransaction card to: receive first information from a merchantmulti-function transaction card; identify a cryptogram based onreceiving the first information from the merchant multi-functiontransaction card; generate a light pattern based on the cryptogram; andprovide, for display, second information based on the light pattern andonly after a mobile device senses a consumer input of the consumer,wherein the consumer input is a sequence, unique to the consumer, andassociated with the mobile device, and wherein the sequence includes: atouch input that relates to an amount of time that the consumer remainedin contact with the consumer multi-function transaction card, and amovement input by the consumer moving the consumer multi-functiontransaction card in a particular motion.
 18. The non-transitorycomputer-readable medium of claim 17, wherein the first informationincludes transaction information associated with a transaction.
 19. Thenon-transitory computer-readable medium of claim 17, wherein the secondinformation is provided only when the consumer multi-functiontransaction card is physically located proximate to a terminalassociated with the first information based on a near-fieldcommunication (NFC) sensor.
 20. The non-transitory computer-readablemedium of claim 17, wherein the sequence further includes one or moreof: a tapping by the consumer on the consumer multi-function transactioncard, a pinching touch by the consumer on the consumer multi-functiontransaction card, or a swiping touch by the consumer on the consumermulti-function transaction card.